|
|||||||||||
| PREV LETTER NEXT LETTER | FRAMES NO FRAMES | ||||||||||
QNAME, a name test which can be one of :
"localname"
"*"
"*:localname"
"*:*"
"prefix:*
"prefix:localname
Possible values for axisStr are :
child
descendant
attribute
self
descendant-or-self
following-sibling
following
namespace
parent
ancestor
preceding-sibling
preceding
ancestor-or-self
Possible values for kindTestStr are :
node()
attribute()
text()
element()
QNAME
XoNode
and its position in document.
XdpNode for any XoNode type
strValue.
val .
XoClassLoader instance with specified parent class loader.
XoClassLoader instance with specified parent class loader.
XoClassLoader instance with an existing XoClassLoader.
XoContainer events listeners.
XoContainer implementation developpers can use, by derivation, to increase productivity
when an XoContainer implementation has no requirement to derive from any specific Java object.XoContentModel represents the unique node to describe a content-model tree. java.beans.Customizer object with a label (displayed in Xotics Editor).
XoDMInstance is the representation of an XML document in Xotics environment.XoFactory is responsible for loading an XoDMInstance object from an XML file,
or creating it from scratch, provided the Registry has appropriate definitions and/or
a specific XML processing instruction included in the parsed file gives the Data-Model definition file location.
XoLockedException with external thread name
attempting to access DM instance while not allowed.
XoObject implementation developpers can use, by derivation,
to increase productivity when an XoObject implementation has no requirement
to derive from any specific Java object.XoObject must
implement this interface. XoRegistry.createXoObject(String, String).
java.beans.PropertyEditor, providing access to
the XoProperty wrapper of an edited property.XoContainer, must be implemented by
all XO Container which can be root of an XO DM instance tree.XoObject implementing this interface is considered as XO Object whose only child
is a XML PCDATA text. XoTextContainer implementation developpers can use to increase productivity
when an XoTextContainer implementation has no requirement to derive from any specific Java object.
XoText implementation developpers can use to increase productivity
when an XoText implementation has no requirement to derive from any specific Java object.XoDMInstance each time an undoable modification has been performed
on DM instance, i.e XoObject adding or removal and property change.XoUndoableEvent must implement this interface.XoDMInstance.release() is called.
|
|||||||||||
| PREV LETTER NEXT LETTER | FRAMES NO FRAMES | ||||||||||